Virtual mobility anchor for network sharing

ABSTRACT

Embodiments are directed to a virtual mobility anchor network element to receive, from a packet gateway (PGW) node, a request for an internet protocol (IP) address for a mobile device, establish an IP address for the mobile device; and provide the IP address to the PGW node in response to the request for the IP address for the mobile device. The virtual mobility anchor network element is configured to receive IP traffic from a network location; determine a target destination for the IP traffic based on a destination IP address, the destination IP address comprising the second IP address; and forward the IP traffic to the PGW node associated with the destination IP address. The virtual mobility anchor network element is also configured to receive IP traffic from the PGW node; determine a target destination for the IP traffic; and route the IP traffic to the target destination.

FIELD

This disclosure pertains to a virtual mobility anchor for networksharing, and more particularly a virtual mobility anchor for Long TermEvolution network sharing.

BACKGROUND

In network sharing, each operator has its own core-network, while theradio network (eNB) is shared. In some cases, the mobility managemententity (MME) is also a shared resource. Owning and managing a corenetwork requires expertise and comes with significant capital andoperational cost. Typically, a Mobile Virtual Network Operator (MVNO)leases access to core network elements owned by a Mobile NetworkOperator (MNO).

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure andfeatures and advantages thereof, reference is made to the followingdescription, taken in conjunction with the accompanying figures, whereinlike reference numerals represent like parts.

FIG. 1 is a schematic block diagram of a wireless network that includesa virtual mobility anchor node in accordance with embodiments of thepresent disclosure.

FIG. 2 is a schematic block diagram of an example mobile virtual networkoperator (MVNO) network node in accordance with embodiments of thepresent disclosure.

FIG. 3 is schematic block diagram of an example mobile device inaccordance with embodiments of the present disclosure.

FIG. 4 is a schematic diagram of a virtual mobility anchor incommunication with a plurality of networks.

FIG. 5 is a process flow diagram for an example initial attachment to anetwork by a virtual mobility anchor in accordance with embodiments ofthe present disclosure.

FIG. 6 is a schematic diagram of a virtual mobility anchor facilitatingroaming between networks in accordance with embodiments of the presentdisclosure.

FIG. 7 is a process flow diagram for facilitating cellular networkoperator roaming in accordance with embodiments of the presentdisclosure.

FIG. 8 is a schematic diagram of a virtual mobility anchor facilitatingroaming between a cellular network and a trusted wireless local areanetwork in accordance with embodiments of the present disclosure.

FIG. 9 is a process flow diagram for facilitating roaming between acellular network and a trusted wireless local area network in accordancewith embodiments of the present disclosure.

FIG. 10 is a schematic diagram of a virtual mobility anchor facilitatingroaming between a cellular network and an untrusted wireless local areanetwork in accordance with embodiments of the present disclosure.

FIG. 11 is a process flow diagram for facilitating roaming between acellular network and an untrusted wireless local area network inaccordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

Network sharing can require each operator to have its own core network(i.e., set of network elements, such as packet gateway (PGW), servinggateway (SGW), mobility management entity (MME), Policy and ChargingRules Function (PCRF), home subscriber server (HSS), etc.), while theradio network (e.g., base station, etc.) is shared between operators.

This disclosure describes a new network-sharing scheme that does notrequire a Mobile Virtual Network Operator (MVNO) to manage a complex setof network functions. Rather, the MVNO can host and manage standardIP-based cloud services that can meet the MVNO's business andarchitectural objectives.

In embodiments, a MVNO can leverage both the radio and core network fromthe Mobile Network Operator (MNO) partners, eliminating the costsinvolved in the core network management, but still retaining control onmobility and IP anchoring of the subscriber sessions. The goal andpurpose of this effort is to facilitate MVNO deployments based onstandard IP cloud-based architectures and overlay models.

Aspects of the embodiments are directed to a virtual mobility anchornetwork element. The virtual mobility anchor network element includes anetwork interface implemented at least partially in hardware and aprocessor implemented at least in hardware. The virtual mobility anchornetwork element is configured to establish an IP address for the mobiledevice and provide the IP address to a packet gateway (PGW) node of amobile network operator (MNO) in response to the request for the IPaddress for the mobile device.

In some implementations of the embodiments, the request for an IPaddress comprises a Dynamic Host Configuration Protocol (DHCP) requestmessage from the PGW node. In some implementations of the embodiments,the DHCP request for an IP address received from the PGW node comprisesone or both of an International Mobile Subscriber Identity (IMSI) or aNetwork Access Identifier (NAI).

In some implementations of the embodiments, the virtual mobility anchornetwork element is further configured to receive IP traffic from anetwork location; determine a target destination for the IP trafficbased on a destination IP address of the mobile device; and forward theIP traffic to a PGW node associated with the destination IP address ofthe mobile device.

In some implementations of the embodiments, the virtual mobility anchornetwork element is further configured to receive IP traffic from the PGWnode; determine a target destination for the IP traffic; and route theIP traffic to the target destination.

In some implementations of the embodiments, the MNO is a first MNO, theIP address is a first IP address and the PGW node is a first PGW node ofthe first MNO. The network interface is configured to receive, from asecond PGW node of a second MNO, a second request for an IP address forthe mobile device. The virtual mobility anchor network element isconfigured to provide the first IP address to the second PGW in responseto the second request for an IP address for the mobile device. In someimplementations of the embodiments, the second request comprises aDynamic Host Configuration Protocol request message.

In some implementations of the embodiments, the first PGW node isassociated with a first core network of the first MNO and the second PGWnode is associated with a second core network of the second MNO.

In some implementations of the embodiments, the virtual mobility anchornetwork element is configured to instruct the first PGW node to forgetand release the first IP address and to discontinue routing IP trafficto the virtual mobility anchor network element.

In some implementations of the embodiments, the virtual mobility anchornetwork element is configured to receive IP traffic from a networklocation; determine a target destination for the IP traffic based on adestination IP address, the destination IP address comprising the secondIP address; and forward the IP traffic to the second PGW node associatedwith the destination IP address.

In some implementations of the embodiments, the virtual mobility anchornetwork element is further configured to receive IP traffic from thesecond PGW node; determine a target destination for the IP traffic; androute the IP traffic to the target destination.

In some implementations of the embodiments, the IP address is a first IPaddress. The network interface is configured to receive, from a wirelessaccess gateway (WAG) node associated with a wireless local area network(WLAN), a second request for an IP address for the mobile device. Thevirtual mobility anchor network element is configured to provide thefirst IP address to the WAG node in response to the second request foran IP address for the mobile device. In some implementations of theembodiments, the second request for an IP address comprises a DynamicHost Configuration Protocol request message.

In some implementations of the embodiments, the virtual mobility anchornetwork element is configured to instruct the PGW node to forget andrelease the first IP address and to discontinue routing IP traffic tothe virtual mobility anchor network element.

In some implementations of the embodiments, the virtual mobility anchornetwork element is configured to receive IP traffic from a networklocation; determine a target destination for the IP traffic based on adestination IP address, the destination IP address comprising the secondIP address; and forward the IP traffic to the WAG node associated withthe destination IP address.

In some implementations of the embodiments, the virtual mobility anchornetwork element is further configured to receive IP traffic from themobile device associated with the WAG node; determine a targetdestination for the IP traffic; and route the IP traffic to the targetdestination.

In some implementations of the embodiments, the IP address is a first IPaddress. The network interface is configured to receive, from an IPsecurity gateway (IPsec GW) node associated with a wireless local areanetwork (WLAN), a request for an IP address for the mobile device. Thevirtual mobility anchor network element is configured to provide thefirst IP address to the IPsec GW node in response to the request for anIP address for the mobile device. In some implementations of theembodiments, the request comprises a Dynamic Host Configuration Protocolrequest message.

In some implementations of the embodiments, the virtual mobility anchornetwork element is configured to instruct the PGW node to forget andrelease the first IP address and to discontinue routing IP traffic tothe virtual mobility anchor network element.

In some implementations of the embodiments, the virtual mobility anchornetwork element is configured to receive IP traffic from a networklocation, determine a target destination for the IP traffic based on adestination IP address, the destination IP address comprising the secondIP address, and forward the IP traffic to the IPsec GW node associatedwith the destination IP address.

In some implementations of the embodiments, the virtual mobility anchornetwork element is further configured to receive IP traffic from theIPsec GW node; determine a target destination for the IP traffic; androute the IP traffic to the target destination.

In some implementations of the embodiments, the virtual mobility anchornetwork node is associated with a Mobile Virtual Network Operator.

In some implementations of the embodiments, the virtual mobility anchornetwork element is further configured to perform classification ofincoming IP traffic and apply service functions to each packet of theincoming IP traffic.

Aspects of the embodiments are directed to a method performed by avirtual mobility anchor network element implemented at least partiallyin hardware. The method includes receiving, from a packet gateway (PGW)node, a request for an internet protocol (IP) address for a mobiledevice; and establishing an IP address for the mobile device. The methodalso includes providing the IP address to the PGW node in response tothe request for the IP address for the mobile device.

In some implementations of the embodiments, the request for an IPaddress comprises a Dynamic Host Configuration Protocol (DHCP) request.

In some implementations of the embodiments, the request for an IPaddress received from the PGW node comprises one or both of anInternational Mobile Subscriber Identity (IMSI) or a Network AccessIdentifier (NAI).

In some implementations of the embodiments, the method also includesreceiving IP traffic from a network location; determining a targetdestination for the IP traffic based on a destination IP address; andforwarding the IP traffic to a PGW node associated with the destinationIP address.

In some implementations of the embodiments, the method also includereceiving IP traffic from the PGW node; determining a target destinationfor the IP traffic; and routing the IP traffic to the targetdestination.

In some implementations of the embodiments, the IP address is a first IPaddress and the PGW node is a first PGW node. The method also includesreceiving, from a second PGW node, a request for an IP address for themobile device; and providing the first IP address to the second PGW inresponse to the request for an IP address for the mobile device.

In some implementations of the embodiments, the first PGW node isassociated with a first core network and the second PGW node isassociated with a second core network, the first core network differentfrom the second core network.

In some implementations of the embodiments, the method also includesinstructing the first PGW node to forget the first IP address and todiscontinue routing IP traffic to the virtual mobility anchor networkelement.

In some implementations of the embodiments, the method also includesreceiving IP traffic from a network location; determining a targetdestination for the IP traffic based on a destination IP address, thedestination IP address comprising the second IP address; and forwardingthe IP traffic to the second PGW node associated with the destination IPaddress.

In some implementations of the embodiments, the method also includesreceiving IP traffic from the second PGW node; determining a targetdestination for the IP traffic; and routing the IP traffic to the targetdestination.

In some implementations of the embodiments, the IP address is a first IPaddress. The method also includes receiving, from a wireless accessgateway (WAG) node associated with a wireless local area network (WLAN),a request for an IP address for the mobile device; and providing thefirst IP address to the WAG node in response to the request for an IPaddress for the mobile device.

In some implementations of the embodiments, the method also includesinstructing the PGW node to forget the first IP address and todiscontinue routing IP traffic to the virtual mobility anchor networkelement.

In some implementations of the embodiments, the method also includesreceiving IP traffic from a network location; determining a targetdestination for the IP traffic based on a destination IP address, thedestination IP address comprising the second IP address; and forwardingthe IP traffic to the WAG node associated with the destination IPaddress.

In some implementations of the embodiments, the method also includesreceive IP traffic from the WAG node; determine a target destination forthe IP traffic; and route the IP traffic to the target destination.

In some implementations of the embodiments, the IP address is a first IPaddress. The method also includes receiving, from an IP security gateway(IPsec GW) node associated with a wireless local area network (WLAN), arequest for an IP address for the mobile device; and providing the firstIP address to the IPsec GW node in response to the request for an IPaddress for the mobile device.

In some implementations of the embodiments, the method also includesinstructing the PGW node to forget the first IP address and todiscontinue routing IP traffic to the virtual mobility anchor networkelement.

In some implementations of the embodiments, the method also includesreceiving IP traffic from a network location; determining a targetdestination for the IP traffic based on a destination IP address, thedestination IP address comprising the second IP address; and forwardingthe IP traffic to the IPsec GW node associated with the destination IPaddress.

In some implementations of the embodiments, the method also includesreceiving IP traffic from the IPsec GW node; determining a targetdestination for the IP traffic; and routing the IP traffic to the targetdestination.

In some implementations of the embodiments, the virtual mobility anchornetwork node is associated with a Mobile Virtual Network Operator.

In some implementations of the embodiments, the method also includingperforming classification of incoming IP traffic and applying servicefunctions to each packet of the incoming IP traffic.

Aspects of the embodiments are directed to a computer-readablenon-transitory medium comprising one or more instructions for augmentingmetadata of a network service header, that when executed on a processorconfigure the processor to receive, from a packet gateway (PGW) node, arequest for an internet protocol (IP) address for a mobile device; andestablish an IP address for the mobile device; and provide the IPaddress to the PGW node in response to the request for the IP addressfor the mobile device.

In some implementations of the embodiments, the request for an IPaddress comprises a Dynamic Host Configuration Protocol (DHCP) request.

In some implementations of the embodiments, the request for an IPaddress received from the PGW node comprises one or both of anInternational Mobile Subscriber Identity (IMSI) or a Network AccessIdentifier (NAI).

In some implementations of the embodiments, the instructions cause theprocessor to receive IP traffic from a network location; determine atarget destination for the IP traffic based on a destination IP address;and forward the IP traffic to a PGW node associated with the destinationIP address.

In some implementations of the embodiments, the instructions cause theprocessor to receive IP traffic from the PGW node; determine a targetdestination for the IP traffic; and route the IP traffic to the targetdestination.

In some implementations of the embodiments, the IP address is a first IPaddress and the PGW node is a first PGW node; and wherein theinstructions cause the processor to receive, from a second PGW node, arequest for an IP address for the mobile device; and provide the firstIP address to the second PGW in response to the request for an IPaddress for the mobile device.

In some implementations of the embodiments, the first PGW node isassociated with a first core network and the second PGW node isassociated with a second core network, the first core network differentfrom the second core network.

In some implementations of the embodiments, the instructions cause theprocessor to instruct the first PGW node to forget the first IP addressand to discontinue routing IP traffic to the virtual mobility anchornetwork element.

In some implementations of the embodiments, the instructions cause theprocessor to receive IP traffic from a network location; determine atarget destination for the IP traffic based on a destination IP address,the destination IP address comprising the second IP address; and forwardthe IP traffic to the second PGW node associated with the destination IPaddress.

In some implementations of the embodiments, the instructions cause theprocessor to receive IP traffic from the second PGW node; determine atarget destination for the IP traffic; and route the IP traffic to thetarget destination.

In some implementations of the embodiments, the IP address is a first IPaddress; and wherein the instructions cause the processor to receive,from a wireless access gateway (WAG) node associated with a wirelesslocal area network (WLAN), a request for an IP address for the mobiledevice; and provide the first IP address to the WAG node in response tothe request for an IP address for the mobile device.

In some implementations of the embodiments, the virtual mobility anchornetwork element is configured to instruct the PGW node to forget thefirst IP address and to discontinue routing IP traffic to the virtualmobility anchor network element.

In some implementations of the embodiments, the instructions cause theprocessor to receive IP traffic from a network location; determine atarget destination for the IP traffic based on a destination IP address,the destination IP address comprising the second IP address; and forwardthe IP traffic to the WAG node associated with the destination IPaddress.

In some implementations of the embodiments, the instructions cause theprocessor to receive IP traffic from the WAG node; determine a targetdestination for the IP traffic; and route the IP traffic to the targetdestination.

In some implementations of the embodiments, the IP address is a first IPaddress; and wherein the instructions cause the processor to receive,from an IP security gateway (IPsec GW) node associated with a wirelesslocal area network (WLAN), a request for an IP address for the mobiledevice; and provide the first IP address to the IPsec GW node inresponse to the request for an IP address for the mobile device.

In some implementations of the embodiments, the instructions cause theprocessor to instruct the PGW node to forget the first IP address and todiscontinue routing IP traffic to the virtual mobility anchor networkelement.

In some implementations of the embodiments, the instructions cause theprocessor to receive IP traffic from a network location; determine atarget destination for the IP traffic based on a destination IP address,the destination IP address comprising the second IP address; and forwardthe IP traffic to the IPsec GW node associated with the destination IPaddress.

In some implementations of the embodiments, the instructions cause theprocessor to receive IP traffic from the IPsec GW node; determine atarget destination for the IP traffic; and route the IP traffic to thetarget destination.

In some implementations of the embodiments, the virtual mobility anchornetwork node is associated with a Mobile Virtual Network Operator.

In some implementations of the embodiments, the instructions cause theprocessor to perform classification of incoming IP traffic and applyservice functions to each packet of the incoming IP traffic.

Aspects of the embodiments are directed to an Internet gateway nodeimplemented at least partially in hardware, the Internet gateway nodeassociated with a mobile network operator (MNO), the Internet gatewaynode including a network interface implemented at least partially inhardware; and a processor implemented at least partially in hardware.The Internet gateway node is configured to send a request for anInternet Protocol (IP) address to a virtual mobility anchor nodeassociated with a mobile virtual network operator (MVNO) for a userequipment (UE); receive an IP address from the virtual mobility anchornode; and allocate the IP address to the UE.

In some implementations of the embodiments, the Internet gateway node isconfigured to receive IP traffic from the UE; and forward the IP trafficto the virtual mobility anchor node.

In some implementations of the embodiments, Internet gateway node isconfigured to receive IP traffic from the virtual mobility anchor nodedestined for the UE; and forward the IP traffic to the UE.

In some implementations of the embodiments, the Internet gateway nodeaos includes one of a packet gateway (PGW), a Wireless Access Gateway(WAG), or an IP Security Gateway (IPsec GW). In some implementations ofthe embodiments, the PGW is configured to operate in local breakout mode(LBO).

In some implementations of the embodiments, the request comprises aDynamic Host Configuration Protocol (DHCP) request.

Aspects of the embodiments are directed to a method performed on anInternet gateway node implemented at least partially in hardware, theInternet gateway node associated with a mobile network operator (MNO).The method includes sending a Dynamic Host Configuration Protocol (DHCP)request for an Internet Protocol (IP) address to a virtual mobilityanchor node associated with a mobile virtual network operator (MVNO) fora user equipment (UE); receiving an IP address from the virtual mobilityanchor node; and allocating the IP address to the UE.

In some implementations of the embodiments, the method also includesreceiving IP traffic from the UE; and forwarding the IP traffic to thevirtual mobility anchor node.

In some implementations of the embodiments, the method also includesreceiving IP traffic from the virtual mobility anchor node destined forthe UE; and forwarding the IP traffic to the UE.

In some implementations of the embodiments, the Internet gateway nodecomprises one of a packet gateway (PGW), a Wireless Access Gateway(WAG), or an IP Security Gateway (IPsec GW). In some implementations ofthe embodiments, the PGW is configured to operate in local breakout mode(LBO).

Aspects of the embodiments are directed to a mobile virtual network thatincludes a home subscriber server (HSS) implemented at least partiallyin hardware, the HSS comprising a database of subscribers and, for eachsubscriber, information about authorized cellular networks eachsubscriber is authorized to connect to. The HSS is configured to receivea request for authentication of user equipment (UE) to connect to acellular network from a mobility management entity associated with thecellular network; and determine that the UE is authorized to connect tothe cellular network. A virtual mobility anchor network elementimplemented at least partially in hardware is configured to establish anInternet Protocol address for the UE; and provide the IP address to anInternet gateway node associated with the cellular network.

In some implementations of the embodiments, the HSS is configured toreceive location update information about a location of the UE. In someimplementations of the embodiments, the HSS is configured to determinethat the UE is authorized to access a plurality of cellular networks ina location; determine a preferred cellular network from the plurality ofcellular networks; and authenticate the UE to connect to the preferredcellular network. In some implementations of the embodiments, the HSSdetermines the preferred cellular network based on one or more of aquality of service of the preferred cellular network, subscriptionparameters for the UE, or pricing. In some implementations of theembodiments, the plurality of cellular networks comprises a plurality ofcellular networks associated with different mobile network operators.

FIG. 1 is a schematic block diagram of a wireless network 100 thatincludes a mobile virtual network operator hosting a virtual mobilityanchor node in accordance with embodiments of the present disclosure.The wireless network 100 includes a mobile virtual network operator(MVNO) 102 that can communicate with one or more networks, such as thatoperated by mobile network operator (MNO)-A 110 and MNO-B 120. The MVNO102 can include one or more servers that provide networkingfunctionality. For example, MVNO 102 includes a virtual mobility anchornode (VMAN) 104 and a home subscriber server 106. The VMAN 104 can beimplemented in hardware, software, or a combination of hardware andsoftware. The VMAN 104 can be, for example, a Dynamic Host ConfigurationProtocol (DHCP) server uses a network protocol used to assign IPaddresses and provide configuration information to devices such asservers, desktops, mobile devices, etc., so they can communicate on anetwork using the Internet Protocol (IP). VMAN104 can be hosted,however, on any network host in the MVNO network 102, and can beinstantiated in a service cloud 108. The VMAN 104 can provide virtualmobility anchoring functionality. Virtual mobility anchoring is afunction that includes allocation of IP address and corresponding IPaddress configuration to the mobile node (or UE per 3GPP terminology)anchored in a MNO network, such as MNO-A 110 or MNO-B 120. The virtualmobility anchoring functionality also includes allocation/de-allocationof IP address management.

In some embodiments, the role of the VMAN 104 also includes mobilitysession management, which can include IP address management andforwarding/routing management for the allocated IP addresses.

The VMAN 104 is aware of the mobile node's current location. Forexample, the VMAN 104 can be in communication with HSS 106, which canreceive location update information from the mobile node throughwhatever network it is connected to. The VMAN 104 also knows whichInternet gateway node (e.g., packet gateway node (PGW) 116 or 126) inthe MNO's network the mobility session is anchored because sessionmanagement includes communications with the Internet gateway node forsession setup, IP management, and forwarding/routing management. TheVMAN 104 can forward all the UE traffic to that Internet gateway node.

The VMAN 104 also performs forwarding/routing management for IP traffic.The VMAN 104 can facilitate service function augmentation 110 to IPpackets. The VMAN 104 can also use packet inspection and othertechniques to collect information about the IP traffic. The meta-datathat gets carried in the network service header includes the mobilenode's identifiers (IMSI, MSISDN, NAI .etc.), MNO/PGW to which themobile is attached and the network location (cell ID/GPS location), etc.This meta-data can be used by other network function in the servicechain for providing other capabilities such as accounting, NetworkAddress Translation, Deep Packet Inspection, etc.

The VMAN 104 can be in communication with one or more MNO networksthrough an interconnect, such as a multi-protocol label switching (MPLS)interconnect 130. The MPLS interconnect 130 can facilitatecommunications between the MVNO 102 and each of MNO-A 110 and MNO-B 120.Additionally, the MPLS interconnect 130 can facilitate communicationsbetween MNO-A 110 and MNO-B 120.

The MNO network can include one or more core network elements that allowa mobile device or UE to communicate with other mobile devices through acellular network or IP network. An example MNO network can include onthat provides cellular services using LTE.

MNO-A 110 can include core network elements, such as a packet gateway(PGW) 116, a mobility management entity (MME) 114, and a serving gateway(SGW) 118, as well as other core network elements. The MNO-A 110 canalso include one or more base stations that can provide an air interfacebetween the core network and the mobile device. For example, for an LTEnetwork, the MNO-A 110 can include eNB 112A, eNB 112B, etc.

The PGW 116 can be considered an Internet gateway node. The internetgateway node can include a network interface implemented at leastpartially in hardware and a processor implemented at least partially inhardware. The Internet gateway node configured to send a request for anInternet Protocol (IP) address to a virtual mobility anchor nodeassociated with a mobile virtual network operator (MVNO) for a userequipment (UE). The Internet gateway node can receive an IP address fromthe virtual mobility anchor node and allocate the IP address to the UE.The Internet gateway node can also be configured to receive IP trafficfrom the UE and forward the IP traffic to the virtual mobility anchornode. The Internet gateway node can receive IP traffic from the virtualmobility anchor node destined for the UE and forward the IP traffic tothe UE. The Internet gateway node can be one of a packet gateway (PGW),a Wireless Access Gateway (WAG), or an IP Security Gateway (IPsec GW).

MNO-A 120 can include core network elements, such as a packet gateway(PGW) 126, a mobility management entity (MME) 124, and a serving gateway(SGW) 128, as well as other core network elements. The MNO-A 120 canalso include one or more base stations that can provide an air interfacebetween the core network and the mobile device. For example, for an LTEnetwork, the MNO-A 120 can include eNB 122A, eNB 122B, etc. As will beunderstood from other portions of this disclosure, the MNO network canbe other types of networks, such as wireless local area networks, whichmay include other network elements.

In embodiments of the disclosure, the MVNO 104 can providecommunications services through an MNO's network without having to leasethe core network elements from the MNO. Embodiments of the disclosurefacilitate minimizing such architectural dependencies and allow MVNOs104 to give more options to the subscriber for connecting tocommunications services architectures.

In the current disclosure, it is assumed that the MVNO 104 owns thesubscriber and the decision on what networks to connect in what areas isfor allowing the MVNO to dictate. An MVNO is configured to be able toestablish wholesale agreement with multiple MNO's, Broadband Operatorsand with Wi-Fi service providers. Based on the location and pricingagreements associated with various MNO agreements, the MVNO can decidewhich MNO network that the device should attach to.

The MVNO network 104 is configured to control device authentication andauthorization to the mobile network. The MVNO network 104 is notrequired to operate the core network, or any of the core functions.Rather, the MNO network 110 or 120 provides the core network elementsand radio access network (RAN) elements. The minimal requirement is forthe MVNO network 104 to host the HSS for controlling the deviceauthentication and service authorization and to provide virtual mobilityanchoring functionality, as described above.

MVNO network 104 is configured to perform accounting on the mobiletraffic and should be able to enforce dynamic QoS support on the mobiletraffic.

MVNO network 104 is configured to obtain the location information of themobile device.

The mobile device's IP traffic enters and exits from the MVNO's IP cloudto facilitate, among other things, analytics and targeted advertising.

Optimized IP mobility support is provided by the VMAN 102 for a mobileroaming between two MNO partner networks. The LTE PGW hosting thesession may change from one MNO's network to the other, but IP addresscontinuity is supported by the VMAN 102 management of IP addressconfiguration.

Virtual Mobility Anchor

To support the above-identified requirements for LTE network sharing,the subscriber's IP session is topologically anchored in the MVNOnetwork 102, but the corresponding LTE session is anchored in the corenetwork of the MNO network 110 or 120. There are essentially two anchorsfor any subscriber's session, an IP anchor in the MVNO network 102 and aLTE session anchor in the MNO network 110 or 120. The function anchoringthe IP session in the MVNO network is referred to as a Virtual MobilityAnchor (VMA) hosted in a VMAN 104, and the function anchoring the LTEsession in the core network is the standard 3GPP PGW function. This twonode IP anchoring relation is realized by steering the traffic from theVMAN 104 to the PGW that is currently hosting a LTE subscriber session.

All the subscriber's IP traffic is routed through the VMAN 104 and theMVNO network 102 retains control on the subscriber's traffic. The MVNOnetwork 102 is not required to host any of the 3GPP core networkfunctions or the radio network. The VMAN 104 will run the subscriberflows through the generic IP service functions in the cloud for anyservice requirements.

The approach does not require a new signaling interface between the PGW116 and the VMAN 104. Dynamic Host Configuration Protocol (DHCP)triggers from the PGW 116 can be used to replace the mobility signalingevents. Optionally, other interfaces can be used in addition to DHCP.These interfaces are for the network functions in the MNO and MVNO torequest/release IP address configuration.

The PGW 116 is configured to receive IP address configuration andallocation information from the VMAN 104. The PGW 116 can provide the IPaddress configuration and allocation to the mobile device that ismanaged by the MVNO network 102 and attempting to use the core network110 or 120 for communications. The IP traffic for the mobile device isrouted through the PGW 116 and the MVNO network 102.

Assumptions

The IMSI/MSISDN space allocated to the MVNO subscriber's mobile devicesare from the MVNO space. The HSS 106 is operated by the MVNO network102.

Device authentication and authorization is controlled by HSS 106. TheHSS 106 will be connected to the global inter-operator InternetworkPacket Exchange (IPX) network.

Inter-connect roaming agreements exist between partner MNO's and theMVNO. Typical options for interconnect include L2/L3 VPN's, or overlaytunnels between PGW and the VMAN 104.

The MVNO's APN is hosted by the PGWs 116 or 126 in each of the partnerMNO networks 110 or 120, respectively. The DNS resolutions of the APN inany of the MNO networks always point to the PGWs in the respective MNO'snetwork hosting that APN.

In embodiments, the PGWs hosting the MVNO's APN can be configured tooperate in Local-Breakout (LBO) mode. However, the LBO traffic is notoffloaded to Internet but the traffic is routed to MVNO's network overthe L2/L3 VPN to the VMAN 104.

Virtual Mobility Anchor Considerations

The virtual mobility anchor is a function that can be collocated withthe DHCP server. A DHCP server that includes a virtual anchor functioncan be considered a virtual mobility anchor node (VMAN), such as VMAN104. The VMAN 104 provides virtual mobility anchoring functionality,which is a lightweight function for managing IP forwarding states. TheVMAN 104 interfaces with the collocated DHCP server, monitors the DHCPevents and manages the forwarding for the DHCP allocatedaddresses/prefixes. Virtual mobility anchor has no awareness to anyspecific system architecture, or it has any access awareness; thefunctionality is an IP layer forwarding function.

Any time an access specific function such as Broadcast Network Gateway(BNG), PGW or IPsec gateway sends a DHCP Request, the message istunneled/routed to the VMAN 104. The VMAN 104 allocates the IPaddress/prefix and also sets up the IP forwarding towards the accessnetwork that made the request. The DHCP request will be included in theIMSI/MSISDN as the client identifier and these identifiers will be usedfor session correlation. The proposed approach does not result in anyhost route pollution, as the addresses are present only in the sharedMNO-MVNO VRF context and the state is present only in the VMAN 104.

FIG. 2 is a schematic block diagram of an example mobile virtual networkoperator (MVNO) network 200 in accordance with embodiments of thepresent disclosure. The MVNO network 200 can include network elementsthat facilitate communication for a mobile device through a mobilenetwork operator (MNO). For example, the MVNO network 200 includes aprocessor 202 implemented at least partially in hardware and a memory206. The MVNO network 200 can include a home subscriber server (HSS)208. The virtual mobility anchor 204 can be instantiated on a serverassociated with the MVNO network 200, such as the DHCP server. Ingeneral, the virtual mobility anchor 204 can reside on a virtualmobility anchor node (VMAN).

The HSS 208 can include a database that contains user-related andsubscriber-related information. The user-related information andsubscriber-related information can include information that allows theHSS 208 to help in selecting and connecting to a MNO managed network.For example, the HSS 208 can include a list of approved networks thatthe user's subscription to one or more networks, a quality of servicethreshold for connecting to or changing networks, pricing informationfor dynamically connecting to different networks, etc.

The HSS 208 also provides support functions in mobility management, calland session setup, user authentication and access authorization. Inembodiments, the HSS 208 can provide a list of ordered and preferrednetworks to the mobile device as to which preferred network it shouldattach to. The HSS 208 can provide this information dynamically based onlocation/time of the day/policy.

The MVNO network 200 can include a radio transceiver 210 forcommunicating with other entities, such as an MNO network or through aMPLS interconnect or through the Internet. The radio transceiver 210 canalso be used to receive IP traffic and forward IP traffic to and fromthe mobile device. The server serving the virtual mobility anchor 204can also process incoming IP traffic for traffic analysis 214. Thevirtual mobility anchor 204 can also facilitate service functionaugmentation to IP packets.

FIG. 3 is schematic block diagram of an example mobile device 300 inaccordance with embodiments of the present disclosure. The mobile device300 can be a user equipment, to use 3GPP terminology. The mobile device300 can be a cellular phone, smart phone, tablet device, laptopcomputer, or other mobile device.

The mobile device 300 includes a processor 302 implemented at leastpartially in hardware and a memory 304 for storing instructions. Themobile device 300 also includes a user interface 308 for allowing a userto interact with the mobile device 300 and to send and receiveinformation from network locations, such as from the Internet or fromother mobile devices or other devices in general. The mobile device 300also includes a radio transceiver 306 configured to transmit and receivewireless signals.

The mobile device 300 is configured to search for networks and attemptto attached to a network to facilitate wireless communications. Inembodiments of the disclosure, the mobile device 300 is configured to beable to communicate through any subscribed network, and is not limitedto a single MNO's network due to the mobile device 300 associated withthe MNO. Rather, the mobile device 300 is associated with an MVNO thatprovides a virtual mobility anchor functionality, which allows themobile device 300 to connect to any of a plurality of MNO networks. Themobile device 300 can scan for any available network, or any availablenetwork available for the user subscription, which includes networksowned/operated by more than one MNO.

FIG. 4 is a schematic diagram of a virtual mobility anchor incommunication with a plurality of networks. The virtual mobility anchor402 (shown as V-Anchor 402 in FIG. 4) can be in communication with amobile device 414 through a communications connection, such as throughan IP network 408. The virtual mobility anchor 402 is instantiated in aservice cloud associated with an MVNO, which manages the IP sessions forthe mobile device 414. The IP traffic from the mobile device 414 isdirected from the MNO network 1 404 to which the mobile device isattached to the virtual mobility anchor 402. The virtual mobility anchor402 performs forwarding and routing of the IP traffic to a networkdestination, such as the Internet 412 or to destination addresses atother networks 406 or to other mobile devices. Additionally, the virtualmobility anchor 402 can facilitate service function chaining, such asdeep packet inspection, addition of firewall, etc.

Approaches for roaming and network selection in 3GPP are typically basedon a static policy, and the home operator does not influence thedecision of the access operator dynamically on a location/time basis.Static policies cannot provide variability in connection options basedon different pricing agreements the MVNO may have with differentoperators in different locations. The ability to influence the selectionof the MNO network on a location basis is described below. This approachallows dynamic selection of the roaming partner at the time of HSSattach.

Current 3GPP specifications such as TS 29.272 (S6a) are not designed todirect the roaming UE to a specific roaming network if more roamingnetworks are available in the specific roaming location. The roaming UEis using the preferential static list stored in the device to select aroaming network. The list of networks is static and may not be updateddynamically when the UE is roaming.

This disclosure describes modifying the parameters (informationelements) in the existing 3GPP procedures to provide information fromthe home HSS at the MVNO network to the roaming UE to attach to aspecific targeted network in the specific location based on specificinformation. Instead of the roaming UE having a provisioned list ofpreferred networks and the set of priorities identifying which networkto select if more networks are available at the specific roaminglocation, this disclosure describes using the MME-HSS procedures anddirecting the roaming UE to attach to a specific network in the roaminglocation.

FIG. 5 is a process flow diagram 500 for an example initial attachmentto a network by a virtual mobility anchor in accordance with embodimentsof the present disclosure. The UE can trigger an initial attachment toan MNO's network using standard session set up, such as RRC connectionsetup and/or attachment requests (502). The UE can communicate through aradio access network (RAN) base station with an MME. The UE provides thePLMNIDs of all visible MNO networks in the initial attachment requestsent to the MME.

The MME in the visited network sends an Authentication InformationRequest (AIR) S6a message to the UE's home HSS (504). The AIR S6amessage carries IMSI, visited PLMN-ID, etc. Based on AIR messageinformation, the home HSS will accept the request for attachment basedon the device credential and the roaming network business agreements.The MME can authenticate the UE (506). At this point, however, the homeHSS does not know where the UE is geographically located and does notknow what the roaming UE location is for allowing the roaming UEauthentication.

In order to instruct the roaming UE from the home HSS what network toconnect to, the Authentication-Information-Request (AIR) message carriesadditional parameters that indicate the roaming geographic UE locationthat will be provided by the visited MME that received the NAS messagefrom the roaming UE. The Update-Location-Request (ULR) S6a message canbe sent from the MME in the visited network to the home HSS to providethe identity of the visited MME currently serving the roaming UE (508).Additionally, the home HSS can include policy information andinformation elements for the mobile device, such as subscriberinformation. Based on that new location information received in the AIRmessage and the subscriber information, the home HSS will respond withAuthentication-Information-Answer (AIA) message with the followingrelevant result parameter values:

Success—it is indication to the roaming UE to attach to the visitedPLMN;

Error code that would represent the new visited PLMN that the roaming UEshould connect. Based on this error code it will indicated to thevisited MME not to allow the roaming UE to attach. The error code wouldbe delivered to the roaming UE and it will be used by the UE to attachto another visited PLMN that is better suited for that location. TheError code can be included with a message indicating a list of preferrednetworks as an ordered list to which the mobile device can attach.

The UE can then make an EUTRAN Radio Access Bearer request to thevisited MME (510). The visited MME can then perform a default S5 bearersetup with the visited packet gateway (PGW) (512). The visited PGW canthen perform a DHCP request (through a DHCP request message) to thevirtual mobility anchor (514). The virtual mobility anchor canallocation an IP address for the UE and provide the IP address to thePGW. The PGW can then provide the IP address configuration to the UE(516). The allocated address can be IPv4 and/or IPv6 address or aprefix. In other words, the IP address can be a single 32-bit IPv4address or a set of IPv4 addresses; and/or single IPv6 prefix/subnet ora set of IPv6 prefixes.

IP traffic from the UE is routed through the visited PGW to the virtualmobility anchor, and the virtual mobility anchor routs IP traffic to theUE through the visited PGW (518).

In some embodiments, the PGW can be configured to operate in LBO mode.IP traffic is forwarded towards the virtual mobility anchor in the VRFcontext.

FIG. 6 is a schematic diagram 600 of a virtual mobility anchorfacilitating roaming between networks in accordance with embodiments ofthe present disclosure. The system architecture of FIG. 6 is similar tothat of FIG. 4. The virtual mobility anchor 602 facilitates transitionof the UE 610 from one MNO network 604 to another MNO network 606. Thecommunication can be performed through an IP network 608. The virtualmobility anchor 602 provides the same IP address to the new MNO network606 that it used for the previous IP session with the first MNO network604.

FIG. 7 is a process flow diagram 700 for facilitating cellular networkoperator roaming in accordance with embodiments of the presentdisclosure. For FIG. 7, the UE has performed an initial attachment to afirst MNO network, as described in FIG. 5. The UE can trigger a handoverfrom a first MNO network to a second MNO network, and can send anattachment request, such as a RRC connection setup and/or attachmentrequest, to the second MNO network (702). The UE can communicate througha radio access network (RAN) base station with an MME of the second MNOnetwork.

The MME in the visited network sends an Authentication InformationRequest (AIR) S6a message to the UE's home HSS (704). The AIR S6amessage carries IMSI, visited PLMN-ID, etc. Based on AIR messageinformation, the home HSS will accept the request for attachment basedon the device credential and the roaming network business agreements.The MME can authenticate the UE (706). At this point, however, the homeHSS does not know where the UE is geographically located and does notknow what the roaming UE location is for allowing the roaming UEauthentication.

In order to instruct the roaming UE from the home HSS what network toconnect to, the Authentication-Information-Request (AIR) message carriesadditional parameters that indicate the roaming geographic UE locationthat will be provided by the visited MME that received the NAS messagefrom the roaming UE. The Update-Location-Request (ULR) S6a message canbe sent from the MME in the visited network to the home HSS to providethe identity of the visited MME currently serving the roaming UE (708).

The UE can then make an EUTRAN Radio Access Bearer request to thevisited MME (710). The visited MME can then perform a default S7 bearersetup with the visited packet gateway (PGW) (712). The visited PGW canthen perform a DHCP request (through a DHCP request message) to thevirtual mobility anchor (714). The DHCP request can serve as a handovertrigger for the virtual anchor to allocate the same IP address the UEwas previously using (in the same IP session but with a different MNOnetwork) to the UE for use with the current MNO network. The virtualmobility anchor can allocation an IP address for the UE and provide theIP address to the PGW. The PGW can then provide the IP addressconfiguration to the UE (716). The virtual mobility anchor can move therouting of IP traffic to MNO-2′s PGW. The route can be added in the VRFcontext. Virtual mobility anchor can send a message, such as a DHCPmessage, to the PGW of the previous MNO network (MNO-1) requestingrelease of the IP address.

The virtual mobility anchor manages a mobility session. This mobilitysession has a state and that state includes an IP address configurationand a forwarding state. The virtual mobility anchor can create/deletethis state. When there is a session and an associated state, all the UEIP traffic from network-destination first hits the virtual mobilityanchor, which in turn forwards the IP traffic to the PGW where themobile node is anchored. When the session is removed, all the associatedstate is gone and the PGW is notified.

IP traffic from the UE is routed through the visited PGW to the virtualmobility anchor, and the virtual mobility anchor routs IP traffic to theUE through the visited PGW (718). The PGW of MNO-2 (the new MNO network)can route IP traffic to the UE. The PGW can also route outbound IPtraffic to the virtual mobility anchor.

FIG. 8 is a schematic diagram 800 of a virtual mobility anchorfacilitating roaming between a cellular network and a trusted wirelesslocal area network in accordance with embodiments of the presentdisclosure. The virtual mobility anchor 802 can manage IP sessions withtrusted wireless local area networks, such as trusted Wi-Fi networks8040. The virtual mobility anchor 802 can communicate with wirelessaccess gateway (WAG) instances 808 instantiated on virtual machines. TheWAG can be virtualized for communications with the Wi-Fi network andcorresponding connected devices 814. The virtual mobility anchor candirect IP traffic from the Internet 812 or other network locations to amobile device 814 via a trusted Wi-Fi network. The virtual mobilityanchor 802 can also perform service function augmentation of IP packets(810).

FIG. 9 is a process flow diagram 900 for facilitating roaming between acellular network and a trusted wireless local area network in accordancewith embodiments of the present disclosure. At the outset, the UE isattached to a first MNO network, which can be an LTE network. Theexisting IP routing is pointing to the first MNO network. The UE movesto a Wi-Fi network trusted by the MVNO managing the UE's mobilitysession.

The access point of the Wi-Fi network can provide Ethernet over aGeneric Routing Encapsulation tunneling (902). The UE can beginattachment to an access point (AP) via an open association (904). The APcan send the UE an Extensible Authentication Protocol (EAP) ID request(906). The UE can respond to the AP with an EAP ID response, that caninclude an IMSI. The AP can transmit the EAP over a secure connection toan Authentication, Authorization, and Accounting (AAA) server (910). Insome embodiments, the AP can use a RADIUS server for authentication. TheAP and the AAA server can exchange information to perform theauthentication and authorization for the UE's attachment to the AP. TheAAA server can then transmit an EAP success message to the AP thatincludes the IMSI and the MSISDN (912).

The UE can then send a DHCP request to the AP (914). The AP forwards theDCHP request to the WAG (916). The WAG can then a RADIUS access requestto the AAA server (918). The AAA server provides an accept message backto the WAG (920). The WAG can then send a DHCP request to the virtualmobility anchor (922). The virtual mobility anchor can send a DHCPresponse to the WAG (924). The DHCP request can server as a handovertrigger. The virtual mobility anchor can use UE identificationinformation and other information to assign a previously allocated IPaddress to the WAG for use in the handover IP session. The virtualmobility anchor can move routing from the PGW of the first MNO networkto the WAG of the trusted WLAN. The virtual mobility anchor can also adda route in VRF context. The virtual mobility anchor can also send a DHCPmessage to the PGW of the first MNO network instructing the PGW torelease the IP address so it can be used in the current IP session withthe WAG.

The WAG can send the DHCP offer to the AP that includes the IP addressconfiguration (926). The AP can forward the DHCP offer to the UE to setup the communications channel (928). IP traffic to and from the UE cannow be managed by the virtual mobility anchor through the AP and the WAG(930). The virtual mobility anchor can perform classification andservice function augmentation on IP packets.

FIG. 10 is a schematic diagram 1000 of a virtual mobility anchorfacilitating roaming between a cellular network and an untrustedwireless local area network in accordance with embodiments of thepresent disclosure. The virtual mobility anchor 1002 can manage IPsessions for a mobile device 1014 through an attachment to an untrustedwireless local area network (such as a Wi-Fi connection) 1004 through aninternet connection 1012 (such as IPsec or SSL based access). Thevirtual mobility anchor 1002 can communicate with the untrusted Wi-Fi1004 through a security gateway 1008 virtualized from among a set ofsecurity gateways 1006. IP traffic is routed through the virtualmobility anchor 1002 to network locations, such as the Internet 1012.The virtual mobility anchor can provide service function chaining 1010.

FIG. 11 is a process flow diagram 1100 for facilitating roaming betweena cellular network and an untrusted wireless local area network inaccordance with embodiments of the present disclosure. At the outset,the UE is attached to a first MNO network, which can be an LTE network.The existing IP routing is pointing to the first MNO network. The UEmoves to an untrusted Wi-Fi network.

The UE can include an IPsec client. The UE can attempt to set up asecure association with the IPsec Gateway (IPsec GW) (1102). The UE canuse the Internet Key Exchange protocol to engage in dialog with theIPsec GW to initialize the secure associate with the IPsec GW. The IPsecGW can authorize the UE to establish the secure association (1104). TheIPsec GW can send an EAP message to the AAA server as access request(1106). The AAA server can provide an access request acceptance messageto the IPsec GW (1108). The IPsec GW can send a DHCP request message tothe virtual mobility anchor (1110). The DHCP request message can serveas a trigger for the handover from the first MNO network to theuntrusted WLAN. The virtual mobility anchor can reassign the IP addressfor the current IP session with the IPsec GW. The IP address that isreassigned is the same IP address used for the UE's IP session with thefirst MNO network's PGW. The virtual mobility anchor can send a DHCPresponse message to the IPsec GW that includes the IP addressconfiguration information (1112). The IPsec GW can send an authorizationresponse message to the UE (1114) to establish the association with theIPsec GW.

The virtual mobility anchor can route IP traffic to and from the UE(1116). The virtual mobility anchor can also send a DHCP message to thePGW of the first MNO instructing the release of the IP address, whichwill now be used in the IP session with the IPsec GW. Additionally, byrouting IP traffic through the virtual mobility anchor, the virtualmobility anchor can facilitate service function augmentation of IPpackets and classification of IP packets for other reasons, such asaccounting and targeted advertising.

Any of these elements (e.g., the network elements, service nodes, etc.)can include memory elements for storing information to be used inachieving the above features, as outlined herein. Additionally, each ofthese devices may include a processor that can execute software or analgorithm to perform the NSH-related features as discussed in thisSpecification. These devices may further keep information in anysuitable memory element [random access memory (RAM), ROM, EPROM, EEPROM,ASIC, etc.], software, hardware, or in any other suitable component,device, element, or object where appropriate and based on particularneeds. Any of the memory items discussed herein should be construed asbeing encompassed within the broad term ‘memory element.’ Similarly, anyof the potential processing elements, modules, and machines described inthis Specification should be construed as being encompassed within thebroad term ‘processor.’ Each of the network elements can also includesuitable interfaces for receiving, transmitting, and/or otherwisecommunicating data or information in a network environment.

Additionally, it should be noted that with the examples provided above,interaction may be described in terms of two, three, or four networkelements. However, this has been done for purposes of clarity andexample only. In certain cases, it may be easier to describe one or moreof the functionalities of a given set of flows by only referencing alimited number of network elements. It should be appreciated that thesystems described herein are readily scalable and, further, canaccommodate a large number of components, as well as morecomplicated/sophisticated arrangements and configurations. Accordingly,the examples provided should not limit the scope or inhibit the broadtechniques of using a virtual mobility anchor to allow a user equipmentto connect to one of a plurality of cellular or other wireless networks,as potentially applied to a myriad of other architectures.

It is also important to note that the various steps described hereinillustrate only some of the possible scenarios that may be executed by,or within, the nodes with NSH capabilities described herein. Some ofthese steps may be deleted or removed where appropriate, or these stepsmay be modified or changed considerably without departing from the scopeof the present disclosure. In addition, a number of these operationshave been described as being executed concurrently with, or in parallelto, one or more additional operations. However, the timing of theseoperations may be altered considerably. The preceding operational flowshave been offered for purposes of example and discussion. Substantialflexibility is provided by nodes with a virtual mobility anchor in thatany suitable arrangements, chronologies, configurations, and timingmechanisms may be provided without departing from the teachings of thepresent disclosure.

It should also be noted that many of the previous discussions may implya single client-server relationship. In reality, there is a multitude ofservers in the delivery tier in certain implementations of the presentdisclosure. Moreover, the present disclosure can readily be extended toapply to intervening servers further upstream in the architecture,though this is not necessarily correlated to the ‘m’ clients that arepassing through the ‘n’ servers. Any such permutations, scaling, andconfigurations are clearly within the broad scope of the presentdisclosure.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. In order to assist the UnitedStates Patent and Trademark Office (USPTO) and, additionally, anyreaders of any patent issued on this application in interpreting theclaims appended hereto, Applicant wishes to note that the Applicant: (a)does not intend any of the appended claims to invoke paragraph six (6)of 35 U.S.C. section 112 as it exists on the date of the filing hereofunless the words “means for” or “step for” are specifically used in theparticular claims; and (b) does not intend, by any statement in thespecification, to limit this disclosure in any way that is not otherwisereflected in the appended claims.

LIST OF ABBREVIATIONS

-   3GPP 3rd Generation Partnership Project-   AAA Authentication, Authorization, and Accounting-   AIA Authentication Information Answer-   AIR Authentication Information Request-   APN Access Point Name-   BNG Broadcast Network Gateway-   DHCP Dynamic Host Configuration Protocol-   DNS Domain Name System-   eNB Evolved Node B-   E-RAB E-UTRAN Radio Access Bearer-   E-UTRAN Evolved Universal Terrestrial Radio Access Network-   HSS Home Subscriber Server-   IMSI International Mobile Subscriber Identity-   IPX Internetwork Packet Exchange-   LBO Local Breakout-   LTE Long Term Evolution-   MCC Mobile Country Code-   MME Mobility Management Entity-   MNC Mobile Network Code-   MNO Mobile Network Operator-   MSISDN Mobile Station International Subscriber Directory Number-   MVNO Mobile Virtual Network Operator-   NAI Network Access Identifier-   NAS Non-Access Stratum-   OTT Over the Top-   PCRF Policy Control and Charging Rules Function-   PGW Packet Gateway-   PLMN Public Land Mobile Network-   QoS Quality of Service-   RAN Radio Access Network-   RRC Radio Resource Control-   SGW Serving Gateway-   UE User Equipment-   ULR Update Location Request-   VMAN Virtual Mobility Anchor Node-   VRF Virtual Routing and Forwarding-   WAG Wireless Access Gateway

What is claimed is:
 1. A virtual mobility anchor network elementcomprising: a network interface implemented at least partially inhardware; and a processor implemented at least in hardware; wherein thevirtual mobility anchor network element is configured to: establish anIP address for the mobile device; and provide the IP address to a packetgateway (PGW) node of a mobile network operator (MNO) in response to therequest for the IP address for the mobile device.
 2. The virtualmobility anchor network element of claim 1, wherein the request for anIP address comprises a Dynamic Host Configuration Protocol (DHCP)request message from the PGW node.
 3. The virtual mobility anchornetwork element of claim 2, wherein the DHCP request for an IP addressreceived from the PGW node comprises one or both of an InternationalMobile Subscriber Identity (IMSI) or a Network Access Identifier (NAI).4. The virtual mobility anchor network element of claim 1, wherein thevirtual mobility anchor network element is further configured to:receive IP traffic from a network location; determine a targetdestination for the IP traffic based on a destination IP address of themobile device; and forward the IP traffic to a PGW node associated withthe destination IP address of the mobile device.
 5. The virtual mobilityanchor network element of claim 1, wherein the virtual mobility anchornetwork element is further configured to: receive IP traffic from thePGW node; determine a target destination for the IP traffic; and routethe IP traffic to the target destination.
 6. The virtual mobility anchornetwork element of claim 1, wherein the MNO is a first MNO, the IPaddress is a first IP address and the PGW node is a first PGW node ofthe first MNO; and wherein the network interface is configured toreceive, from a second PGW node of a second MNO, a second request for anIP address for the mobile device; and wherein the virtual mobilityanchor network element is configured to provide the first IP address tothe second PGW in response to the second request for an IP address forthe mobile device, wherein the second request comprises a Dynamic HostConfiguration Protocol request message.
 7. The virtual mobility anchornetwork element of claim 6, wherein the first PGW node is associatedwith a first core network of the first MNO and the second PGW node isassociated with a second core network of the second MNO.
 8. The virtualmobility anchor network element of claim 6, wherein the virtual mobilityanchor network element is configured to instruct the first PGW node toforget and release the first IP address and to discontinue routing IPtraffic to the virtual mobility anchor network element.
 9. The virtualmobility anchor network element of claim 6, wherein the virtual mobilityanchor network element is configured to: receive IP traffic from anetwork location; determine a target destination for the IP trafficbased on a destination IP address, the destination IP address comprisingthe second IP address; and forward the IP traffic to the second PGW nodeassociated with the destination IP address.
 10. The virtual mobilityanchor network element of claim 6, wherein the virtual mobility anchornetwork element is further configured to: receive IP traffic from thesecond PGW node; determine a target destination for the IP traffic; androute the IP traffic to the target destination.
 11. A method performedby a virtual mobility anchor network element implemented at leastpartially in hardware, the method comprising: receiving, from a packetgateway (PGW) node, a request for an internet protocol (IP) address fora mobile device; and establishing an IP address for the mobile device;and providing the IP address to the PGW node in response to the requestfor the IP address for the mobile device.
 12. The method of claim 11,wherein the request for an IP address comprises a Dynamic HostConfiguration Protocol (DHCP) request.
 13. The method of claim 11,wherein the request for an IP address received from the PGW nodecomprises one or both of an International Mobile Subscriber Identity(IMSI) or a Network Access Identifier (NAI).
 14. The method of claim 11,further comprising: receiving IP traffic from a network location;determining a target destination for the IP traffic based on adestination IP address; and forwarding the IP traffic to a PGW nodeassociated with the destination IP address.
 15. The method of claim 11,further comprising: receiving IP traffic from the PGW node; determininga target destination for the IP traffic; and routing the IP traffic tothe target destination.
 16. The method of claim 11, wherein the IPaddress is a first IP address and the PGW node is a first PGW node; andwherein the method further comprises: receiving, from a second PGW node,a request for an IP address for the mobile device; and providing thefirst IP address to the second PGW in response to the request for an IPaddress for the mobile device.
 17. The method of claim 16, wherein thefirst PGW node is associated with a first core network and the secondPGW node is associated with a second core network, the first corenetwork different from the second core network.
 18. The method of claim16, further comprising instructing the first PGW node to forget thefirst IP address and to discontinue routing IP traffic to the virtualmobility anchor network element.
 19. The method of claim 16, furthercomprising: receiving IP traffic from a network location; determining atarget destination for the IP traffic based on a destination IP address,the destination IP address comprising the second IP address; andforwarding the IP traffic to the second PGW node associated with thedestination IP address.
 20. The method of claim 16, further comprising:receiving IP traffic from the second PGW node; determining a targetdestination for the IP traffic; and routing the IP traffic to the targetdestination.
 21. A mobile virtual network comprising: a home subscriberserver (HSS) implemented at least partially in hardware, the HSScomprising a database of subscribers and, for each subscriber,information about authorized cellular networks each subscriber isauthorized to connect to, the HSS configured to: receive a request forauthentication of a user equipment (UE) to connect to a cellular networkfrom a mobility management entity associated with the cellular network;and determine that the UE is authorized to connect to the cellularnetwork; and a virtual mobility anchor network element implemented atleast partially in hardware configured to: establish an InternetProtocol address for the UE; and provide the IP address to an Internetgateway node associated with the cellular network.
 22. The mobilevirtual network of claim 21, wherein the HSS is configured to receivelocation update information about a location of the UE.
 23. The mobilevirtual network of claim 21, wherein the HSS is configured to: determinethat the UE is authorized to access a plurality of cellular networks ina location; determine a preferred cellular network from the plurality ofcellular networks; and authenticate the UE to connect to the preferredcellular network.
 24. The mobile virtual network of claim 23, whereinthe HSS determines the preferred cellular network based on one or moreof a quality of service of the preferred cellular network, subscriptionparameters for the UE, or pricing.
 25. The mobile virtual network ofclaim 23, wherein the plurality of cellular networks comprises aplurality of cellular networks associated with different mobile networkoperators.